Efficient virtual machine scanning

ABSTRACT

A system and method for scanning of virtual machine images. The method includes creating a virtual machine instance of a virtual machine based on a virtual machine image of the virtual machine and an application programming interface (API) of an environment in which the virtual machine is to be deployed, wherein the virtual machine image has an entry point such that the virtual machine instance executes the entry point; and replacing the entry point of the virtual machine instance with a lightweight script, wherein the lightweight script is configured to retrieve a static scanner executable, to execute the static scanner executable, and to send results of the scanning.

TECHNICAL FIELD

The present disclosure relates generally to scanning of virtual machines, and more particularly to techniques for efficiently scanning virtual machines.

BACKGROUND

With the advent of cloud computing, the use of virtual machines has become common practice for many industries. A virtual machine is an emulation of a computer system. Virtual machines allow for greater modularity in computer operation, and can therefore be applied in a wide variety of uses.

In order to utilize virtual machines consistent with applicable compliance policies, customers are required to scan their virtual machine images for compliance and vulnerabilities prior to deployment. This requires additional computing resources on top of the computing resources needed to operate the virtual machines. In particular, existing solutions require the agent performing the scanning to be at the same computer location as the image to be scanned. As a result, these solutions either require downloading the images to be scanned or deployment of an agent at the location where the images are stored. This may slow down the scanning and requires use of dedicated network and storage resources, which in turn may interfere with or impede other processes at that location. Further, when scanning involves analyzing a dynamic instance of an image at runtime, executing the image introduces security risks in the environment in which the image is stored.

It would therefore be advantageous to provide a solution that would overcome the challenges noted above.

SUMMARY

A summary of several example embodiments of the disclosure follows. This summary is provided for the convenience of the reader to provide a basic understanding of such embodiments and does not wholly define the breadth of the disclosure. This summary is not an extensive overview of all contemplated embodiments, and is intended to neither identify key or critical elements of all embodiments nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as a prelude to the more detailed description that is presented later. For convenience, the term “some embodiments” or “certain embodiments” may be used herein to refer to a single embodiment or multiple embodiments of the disclosure.

Certain embodiments disclosed herein include a method for scanning of virtual machine images. The method comprises: creating a virtual machine instance of a virtual machine based on a virtual machine image of the virtual machine and an application programming interface (API) of an environment in which the virtual machine is to be deployed, wherein the virtual machine image has an entry point such that the virtual machine instance executes the entry point; and replacing the entry point of the virtual machine instance with a lightweight script, wherein the lightweight script is configured to retrieve a static scanner executable, to execute the static scanner executable, and to send results of the scanning.

Certain embodiments disclosed herein also include a non-transitory computer readable medium having stored thereon causing a processing circuitry to execute a process, the process comprising: creating a virtual machine instance of a virtual machine based on a virtual machine image of the virtual machine and an application programming interface (API) of an environment in which the virtual machine is to be deployed, wherein the virtual machine image has an entry point such that the virtual machine instance executes the entry point; and replacing the entry point of the virtual machine instance with a lightweight script, wherein the lightweight script is configured to retrieve a static scanner executable, to execute the static scanner executable, and to send results of the scanning.

Certain embodiments disclosed herein also include a system for scanning of virtual machine images. The system comprises: a processing circuitry; and a memory, the memory containing instructions that, when executed by the processing circuitry, configure the system to: create a virtual machine instance of a virtual machine based on a virtual machine image of the virtual machine and an application programming interface (API) of an environment in which the virtual machine is to be deployed, wherein the virtual machine image has an entry point such that the virtual machine instance executes the entry point; and replace the entry point of the virtual machine instance with a lightweight script, wherein the lightweight script is configured to retrieve a static scanner executable, to execute the static scanner executable, and to send results of the scanning.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter disclosed herein is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features, and advantages of the disclosed embodiments will be apparent from the following detailed description taken in conjunction with the accompanying drawings.

FIG. 1 is a network diagram utilized to describe various disclosed embodiments.

FIG. 2 is a flowchart illustrating a method for cost-efficient virtual machine scanning according to an embodiment.

FIG. 3 is a flowchart illustrating a method for creating a lightweight virtual machine instance according to an embodiment.

FIG. 4 is a schematic diagram of a virtual machine scanner according to an embodiment.

DETAILED DESCRIPTION

It is important to note that the embodiments disclosed herein are only examples of the many advantageous uses of the innovative teachings herein. In general, statements made in the specification of the present application do not necessarily limit any of the various claimed embodiments. Moreover, some statements may apply to some inventive features but not to others. In general, unless otherwise indicated, singular elements may be in plural and vice versa with no loss of generality. In the drawings, like numerals refer to like parts through several views.

To address the issues with added computing resources for scanning virtual machines prior to deployment, the disclosed embodiments provide techniques for cost-efficient virtual machine scanning. More specifically, various disclosed embodiments provide techniques for performing compliance and vulnerability scanning which may be utilized for large virtual machine images such as those hosted in cloud computing infrastructures.

The disclosed embodiments further do not require downloading virtual machine images in order to complete scanning. The disclosed embodiments provide advantages such as, but not limited to, reducing download times associated with retrieving virtual machines, improving security of environments in which the virtual machines are to be deployed, allowing for approaches which do not require use of agents or additional deployments in the environment where the virtual machine image is to be deployed, and the like.

The various disclosed embodiments include a method and system for virtual machine scanning. A lightweight virtual machine instance is created in a secure environment based on a virtual machine image and an application programming interface of the environment in which the virtual machine image is to be deployed. In an embodiment, a cost-efficient type of virtual machine may be selected for the lightweight virtual machine to be created.

The cost-efficient type of virtual machine is a type of virtual machine which utilizes excess computing resources rather than dedicated computing resources. As a result, the cost-efficient type of virtual machine provides more efficient use of existing computing resources and allows for the possibility of utilizing types of virtual machines which computing resource providers typically charge less to use. The cost-efficient type of virtual machine may be, for example, a preemptive (also known as pre-emptible) instance or a spot instance.

An image entry point of the virtual machine image is replaced with a lightweight script. The lightweight script is configured to cause scanning the image and to send results of the scan for further use. The script is lightweight in that it does not include all of the code required for scanning and instead uses at least some external code in order to cause the scanning. To this end, the lightweight script may be configured to retrieve and execute a static scanner executable that includes instructions for scanning virtual machine images.

In an embodiment, the lightweight virtual machine instance is configured such that no incoming internal traffic is allowed, only specific applications are allowed to be executed by the virtual machine instance, the lightweight virtual machine instance cannot communicate via unsecured networks, or a combination thereof.

Benefits of some specific aspects of the disclosure may include: creating an instance of a virtual machine image based on an application programming interface instead of downloading the virtual machine image can significantly improve scanning time; and using preemptive virtual machines may reduce computing resource costs significantly.

FIG. 1 shows an example network diagram 100 utilized to describe the various disclosed embodiments. In the example network diagram 100, a client device 120, a virtual machine (VM) scanner 130, and a computing resource provider environment 140 are communicatively connected via a network 110. The network 110 may be, but is not limited to, a wireless, cellular or wired network, a local area network (LAN), a wide area network (WAN), a metro area network (MAN), the Internet, the worldwide web (WWW), similar networks, and any combination thereof.

The client device 120 may be, but is not limited to, a personal computer, a laptop, a tablet computer, a smartphone, a wearable computing device, or any other device capable of receiving user inputs and sending requests via the network 110. The client device 120 may be operated by a user seeking to use one or more virtual machine images among images 145 stored in a virtual machine image database 142 of the computing resource provider environment 140. To this end, in an example implementation, the client device 120 sends a request to the virtual machine scanner 130 to scan one or more of the virtual machine images 145.

The computing resource provider environment 140 is an environment utilized by an entity which remotely provides computing resources and includes the virtual machine image database 142 and one or more provider servers 144. In an example implementation, the computing resource provider environment 140 is a cloud computing environment allowing for running applications at least partially hosted on cloud servers acting as the provider servers 144. Each provider server 144 is configured to provide computing resources for remote processes and is configured to execute instances of the images 145.

In example implementation, the virtual machine image database 142 is configured to store virtual machine images 145. Each image 145 is static data including the software that is executed when a respective virtual machine is executed, for example, via a computing resource provider server 144. The result of executing one of the images 145 is an instance (not shown) of the image 145. Thus, an instance is a dynamic runtime version of a virtual machine image 145 capable of running software such as operating systems, processes, and the like.

The virtual machine scanner 130 is configured to efficiently scan the requested virtual machine images 145 as described herein. In the example implementation shown in FIG. 1, the virtual machine scanner 130 is deployed outside of the computing resource provider environment 140.

The virtual machine scanner 130 is configured to instantiate instances of the virtual machine images 145 in the computing resource environment 140. More specifically, the instances are instantiated via the provider server 144. The virtual machine scanner 130 may be further configured with one or more application programming interfaces used by the virtual machine image database 142 (e.g., application programming interfaces of cloud management platforms hosting the virtual machine image databases, not shown), or may be configured to access such application programming interfaces from such cloud management or other platforms, in order to create lightweight instances of the virtual machine images using such application programming interfaces.

It should be noted that a single virtual machine image database 142 and a single provider server 144 of a single computing resource provider environment 140 are shown in FIG. 1 merely for simplicity purposes, but that the disclosed embodiments may be equally applicable to multiple computing resource provider environments. Further, each computing resource provider environment may include multiple virtual machine image databases, multiple servers, or both, without departing from the scope of the disclosure. Moreover, the virtual machine scanner 130 is depicted as a hardware system, but the virtual machine scanner 130 may be implemented as a virtual component (e.g., a software container or virtual machine) without departing from the scope of the disclosure.

FIG. 2 is an example flowchart 200 illustrating a method for cost-efficient virtual machine scanning according to an embodiment.

At S210, a new lightweight virtual machine instance is created based on a virtual machine image to be scanned. The lightweight virtual machine instance is created in a cost-efficient and secure manner. The lightweight virtual machine instance may be created using computing resources which have access to the location in which the virtual machine image is stored (e.g., one of the provider servers 144 which can access the images 145, FIG. 1). Creating a lightweight virtual machine instance is now described further with respect to FIG. 3.

FIG. 3 is an example flowchart illustrating a method for creating a lightweight virtual machine instance according to an embodiment.

At S310, a type of virtual machine is selected for the lightweight virtual machine instance to be created. In an embodiment, the selected type of virtual machine is a cost-efficient type of virtual machine and may be, but is not limited to, a preemptive virtual machine, a spot instance virtual machine, or another type of virtual machine which utilizes excess computing resources of a computing resource provider (e.g., a cloud provider) and therefore has reduced cost as compared to dedicated computing resources.

At S320, the virtual machine instance is instantiated using the selected type of virtual machine, the virtual machine image, and one or more application programming interfaces (APIs) of the environment in which the original virtual machine image is stored. In an embodiment, the virtual machine instance is instantiated in the same environment in which the virtual machine image is stored (e.g., in a server deployed in a cloud computing environment that also includes a storage in which the virtual machine image is stored).

By using the virtual machine image and such APIs, the image can be accurately scanned without requiring downloading the virtual machine image. This, in turn, reduces the download time needed for obtaining the data to be scanned and, therefore, improves efficiency of the scanning. Additionally, since the image is not downloaded, the disclosed embodiments do not depend on the format of the image. Thus, the instance of the virtual machine image may be created agnostic of formats such as open virtualization format (OVF), Virtual Machine Disk (OMDK), and the like.

In a further embodiment, the lightweight virtual machine instance is created based on a known budget for the scanning and an expected scanning time. The expected time may be determined based on historical scan times for images of various types of virtual machines. More specifically, the expected scanning time is based on a type of virtual machine to be scanned and a size of the virtual machine's image. As a non-limiting example for creating a virtual machine instance based on a known budget and an expected scanning time, historical scan times from scans involving multiple types of virtual machines (as a non-limiting example, virtual machines having specifications such as a1.large, c4.large, t2.micro, etc., of Amazon Web Services®).

In this regard, it is noted that cloud providers such as Google®, Amazon Web Services®, and Azure® may offer cost-efficient virtual machines which utilize excess computing resources. These excess resource virtual machines may be less expensive than dedicated virtual machine hosting but subject to eviction when the computing resources are no longer excess (i.e., when the resources are needed by another process).

It has been identified that the scanning process described herein may effectively use these excess resource virtual machine types since the scanning only requires the resources for a limited period of time (i.e., the scanning will typically be completed before eviction occurs) and, even if eviction occurs, minimal computing resources will have been wasted. Accordingly, the disclosed scanning may take advantage of the cost-efficient nature of these excess resource virtual machines without being significantly impacted by the typical eviction downsides. The result of using such excess resource virtual machine types may be a cost reduction of as much as 90% as compared to using dedicated virtual machine types.

At S330, the instantiated virtual machine instance is reconfigured. The reconfiguration may include any combination of the following settings: no incoming internal traffic is allowed, only specific applications are allowed to run on the lightweight virtual machine instance (e.g., a predetermined whitelisted set of applications); no communications are permitted via unsecured networks; no code that could perform changes in the environment of the lightweight virtual machine instance is permitted to run (e.g., code which would connect to a database of the environment in which the instance is deployed); access is limited to specific systems or storages (e.g., only a designated storage or management console is allowed to be accessed), or a combination thereof. These configurations improve security of the scanning process by restricting communications and software which may be harmful if the image is malicious or otherwise not in compliance with applicable security rules.

Returning to FIG. 2, at S220, an image entry point of the virtual machine image is replaced with a lightweight script. The image entry point is where the first instructions of the virtual machine image are executed. The lightweight script may be, but is not limited to, a binary file that contains compiled machine code. The type of binary depends on the operating system which will be used to executed the lightweight script and may be written using a programming language, but is not limited to, C, C++, JavaScript, Python, and the like.

In an embodiment, the lightweight script is configured to cause scanning of the virtual machine image and to send the results of the scan for further use (e.g., a system deployed in a cloud management platform) such as, but not limited to, the virtual machine scanner 130, FIG. 1. To this end, in an embodiment, the lightweight script may be configured to pull (i.e., retrieve) and execute a static scanner executable. The static scanner executable is an executable file including instructions that, when executed by a processing circuitry, configure the processing circuitry to scan a virtual machine image. The static scanner executable may be pulled, for example, from a software-as-a-service provider system or an on-premises console. Alternatively, the static scanner executable may be uploaded to a region in which the virtual machine scanner operates (e.g., a cloud region) such that it is locally accessible to the virtual machine scanner.

In an embodiment where one or more rules of the computing resource provider environment in which the virtual machine image is to be deployed do not allow for initialization scripts, the lightweight script is stored using a storage mechanism instead of being incorporated into the virtual machine instance. Such storage mechanism may be, but is not limited to, a cloud provider storage resource such as an Amazon® S3 bucket. In such an embodiment, the lightweight script is stored in a location that can be called by the virtual machine instance such that the lightweight script is pulled during execution of a startup script of the virtual machine image. Accordingly, in such an embodiment, rather than replacing the entire entry point with the lightweight script, an instruction to pull and run the lightweight script from the appropriate location may be added to the entry point, thereby replacing the normal entry point with a modified entry point which pulls and runs the scanner executable.

In another embodiment where one or more communication rules of the computing resource provider environment in which the virtual machine image is to be deployed (e.g., cloud provider firewall rules) do not allow for external traffic of nodes therein, the lightweight script is configured to store results of the scan using a storage mechanism of the computing resource provider environment. Such a storage mechanism may be, but is not limited to, a cloud provider storage resource such as an Amazon® S3 bucket. The scan results can be accessed via the cloud provider storage resource by an appropriate entity (e.g., a system managing security in the cloud provider's platform).

At S230, results of the scan are received from the created instance of the virtual machine image. The results of the scan indicate whether the underlying virtual machine image is in compliance with one or more security rules or polices of the entity hosting the virtual machine image and/or whether the underlying virtual machine image exhibits characteristics of any known vulnerabilities.

In some implementations, the scanner executable is configured to check security rules or policies stored in one or more external databases, and to determine whether the scanned image is in compliance with each applicable rule or policy. Such rules or policies may include, but are not limited to, allowing access only to certain systems or groups of systems, creating multiple instances for a single instantiation of a virtual machine, interacting directly with a hypervisor, creating a large (e.g., above a threshold) amount of traffic over a network, interacting with other virtual machines, migrating the virtual machine to a new host, and the like. An image may violate such policies when the image is configured to perform one or more forbidden actions.

As noted above, in some embodiments, the results of the scan may be stored in a storage mechanism of the computing resource provider environment in which the virtual machine image is to be deployed. Accordingly, in such embodiments, the results of the scan may be retrieved from such a storage mechanism instead of being received from the server executing the virtual machine instance.

At optional S240, when results of the scan indicate that the underlying virtual machine image is not in compliance or exhibits a known vulnerability, one or more mitigation actions may be performed. The mitigation actions may include, but are not limited to, removing the virtual machine image from a repository (e.g., the virtual machine image database 142, FIG. 1), sending a notification to a system associated with the environment in which the virtual machine image is hosted (e.g., a cloud provider manager server), both, and the like.

FIG. 4 is an example schematic diagram of a virtual machine scanner 130 according to an embodiment. The virtual machine scanner 130 includes a processing circuitry 410 coupled to a memory 420, a storage 430, and a network interface 440. In an embodiment, the components of the virtual machine scanner 130 may be communicatively connected via a bus 450.

The processing circuitry 410 may be realized as one or more hardware logic components and circuits. For example, and without limitation, illustrative types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), Application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), graphics processing units (GPUs), tensor processing units (TPUs), general-purpose microprocessors, microcontrollers, digital signal processors (DSPs), and the like, or any other hardware logic components that can perform calculations or other manipulations of information.

The memory 420 may be volatile (e.g., random access memory, etc.), non-volatile (e.g., read only memory, flash memory, etc.), or a combination thereof.

In one configuration, software for implementing one or more embodiments disclosed herein may be stored in the storage 430. In another configuration, the memory 420 is configured to store such software. Software shall be construed broadly to mean any type of instructions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Instructions may include code (e.g., in source code format, binary code format, executable code format, or any other suitable format of code). The instructions, when executed by the processing circuitry 410, cause the processing circuitry 410 to perform the various processes described herein.

The storage 430 may be magnetic storage, optical storage, and the like, and may be realized, for example, as flash memory or other memory technology, compact disk-read only memory (CD-ROM), Digital Versatile Disks (DVDs), or any other medium which can be used to store the desired information.

The network interface 440 allows the virtual machine scanner 130 to communicate with the client device 120 for purposes such as for example, receiving requests to scan virtual machine images. The network interface 440 further allows the virtual machine scanner 130 to communicate with the computing resource provider environment 140 in order to scan virtual machine images in accordance with the disclosed embodiments.

It should be understood that the embodiments described herein are not limited to the specific architecture illustrated in FIG. 4, and other architectures may be equally used without departing from the scope of the disclosed embodiments. In particular, the virtual machine scanner 130 is depicted as a hardware device, but can be realized as a software device (e.g., a software container or a virtual machine) executed over a host including at least some of the hardware components described with respect to FIG. 4.

It should be noted that various disclosed embodiments describe a lightweight script as performing various activities for simplicity purposes, but that the lightweight script performs these activities when executed by a virtual machine instance by configuring the virtual machine instance to perform these activities. The lightweight script is executed by a hardware device including a processing circuitry.

The various embodiments disclosed herein can be implemented as hardware, firmware, software, or any combination thereof. Moreover, the software is preferably implemented as an application program tangibly embodied on a program storage unit or computer readable medium consisting of parts, or of certain devices and/or a combination of devices. The application program may be uploaded to, and executed by, a machine comprising any suitable architecture. Preferably, the machine is implemented on a computer platform having hardware such as one or more central processing units (“CPUs”), a memory, and input/output interfaces. The computer platform may also include an operating system and microinstruction code. The various processes and functions described herein may be either part of the microinstruction code or part of the application program, or any combination thereof, which may be executed by a CPU, whether or not such a computer or processor is explicitly shown. In addition, various other peripheral units may be connected to the computer platform such as an additional data storage unit and a printing unit. Furthermore, a non-transitory computer readable medium is any computer readable medium except for a transitory propagating signal.

It should be understood that any reference to an element herein using a designation such as “first,” “second,” and so forth does not generally limit the quantity or order of those elements. Rather, these designations are generally used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements may be employed there or that the first element must precede the second element in some manner. Also, unless stated otherwise, a set of elements comprises one or more elements.

As used herein, the phrase “at least one of” followed by a listing of items means that any of the listed items can be utilized individually, or any combination of two or more of the listed items can be utilized. For example, if a system is described as including “at least one of A, B, and C,” the system can include A alone; B alone; C alone; 2A; 2B; 2C; 3A; A and B in combination; B and C in combination; A and C in combination; A, B, and C in combination; 2A and C in combination; A, 3B, and 2C in combination; and the like.

All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the principles of the disclosed embodiment and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the disclosed embodiments, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure. 

What is claimed is:
 1. A method for scanning of virtual machine images, comprising: creating a virtual machine instance of a virtual machine based on a virtual machine image of the virtual machine and an application programming interface (API) of an environment in which the virtual machine is to be deployed, wherein the virtual machine image has an entry point such that the virtual machine instance executes the entry point; and replacing the entry point of the virtual machine instance with a lightweight script, wherein the lightweight script is configured to retrieve a static scanner executable, to execute the static scanner executable, and to send results of the scanning.
 2. The method of claim 1, further comprising: performing at least one mitigation action based on the results of the scanning.
 3. The method of claim 2, further comprising: retrieving the results of the scanning from a storage.
 4. The method of claim 2, wherein the at least one mitigation action further comprises: removing the virtual machine image from the environment in which the virtual machine is to be deployed.
 5. The method of claim 1, wherein creating the virtual machine instance further comprises: configuring the virtual machine instance with at least one configuration, wherein the at least one configuration includes at least one of: no internal traffic allowed, only predetermined allowable applications are allowed to run, no code which could perform changes in the environment is allowed to run, access is limited, and no communications are allowed via unsecured networks.
 6. The method of claim 1, wherein the created virtual machine instance is a type of virtual machine instance that utilizes excess computing resources of the environment in which the virtual machine is to be deployed.
 7. The method of claim 6, wherein the type of virtual machine instance is any of: a pre-emptible instance, and a spot instance.
 8. The method of claim 6, wherein the lightweight virtual machine instance is created based on a known budget and an expected scanning time.
 9. The method of claim 1, further comprising: storing the lightweight script in a storage location accessible to the virtual machine instance.
 10. The method of claim 1, wherein replacing the entry point of the virtual machine instance with the lightweight script further comprises adding an instruction to retrieve the lightweight script from the storage location and to run the retrieved lightweight script.
 11. A non-transitory computer readable medium having stored thereon instructions for causing a processing circuitry to execute a process, the process comprising: creating a virtual machine instance of a virtual machine based on a virtual machine image of the virtual machine and an application programming interface (API) of an environment in which the virtual machine is to be deployed, wherein the virtual machine image has an entry point such that the virtual machine instance executes the entry point; and replacing the entry point of the virtual machine instance with a lightweight script, wherein the lightweight script is configured to retrieve a static scanner executable, to execute the static scanner executable, and to send results of the scanning.
 12. A system for scanning of virtual machine images, comprising: a processing circuitry; and a memory, the memory containing instructions that, when executed by the processing circuitry, configure the system to: create a virtual machine instance of a virtual machine based on a virtual machine image of the virtual machine and an application programming interface (API) of an environment in which the virtual machine is to be deployed, wherein the virtual machine image has an entry point such that the virtual machine instance executes the entry point; and replace the entry point of the virtual machine instance with a lightweight script, wherein the lightweight script is configured to retrieve a static scanner executable, to execute the static scanner executable, and to send results of the scanning.
 13. The system of claim 12, wherein the system is further configured to: perform at least one mitigation action based on the results of the scanning.
 14. The system of claim 13, wherein the system is further configured to: retrieve the results of the scanning from a storage.
 15. The system of claim 13, wherein the at least one mitigation action further comprises: removing the virtual machine image from the environment in which the virtual machine is to be deployed.
 16. The system of claim 12, wherein the system is further configured to: configure the virtual machine instance with at least one configuration, wherein the at least one configuration includes at least one of: no internal traffic allowed, only predetermined allowable applications are allowed to run, no code which could perform changes in the environment is allowed to run, access is limited, and no communications are allowed via unsecured networks.
 17. The system of claim 12, wherein the created virtual machine instance is a type of virtual machine instance that utilizes excess computing resources of the environment in which the virtual machine is to be deployed.
 18. The system of claim 17, wherein the type of virtual machine instance is any of: a pre-emptible instance, and a spot instance.
 19. The system of claim 17, wherein the lightweight virtual machine instance is created based on a known budget and an expected scanning time.
 20. The system of claim 12, wherein the system is further configured to: store the lightweight script in a storage location accessible to the virtual machine instance.
 21. The system of claim 12, wherein the system is further configured to: adding an instruction to retrieve the lightweight script from the storage location and to run the retrieved lightweight script. 